Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1726

reference
710-tree-1
name
1726
tree-preservation-order

undefined

710-tpo-1
uprn
address-text
point
POINT (-1.005117 50.862644)
geometry
MULTIPOLYGON (((-1.005003 50.862632,-1.005008 50.862654,-1.005024 50.862674,-1.005049 50.862691,-1.005080 50.862701,-1.005115 50.862705,-1.005150 50.862702,-1.005182 50.862692,-1.005208 50.862676,-1.005224 50.862656,-1.005230 50.862634,-1.005225 50.862612,-1.005210 50.862591,-1.005185 50.862575,-1.005153 50.862565,-1.005118 50.862561,-1.005083 50.862564,-1.005051 50.862574,-1.005026 50.862590,-1.005009 50.862610,-1.005003 50.862632)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL